Skip to content

NO-ISSUE: chore: bump quay master version - #83122

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
jbpratt:bump-quay-master
Aug 10, 2026
Merged

NO-ISSUE: chore: bump quay master version#83122
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
jbpratt:bump-quay-master

Conversation

@jbpratt

@jbpratt jbpratt commented Aug 7, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Contributor

Signed-off-by: Brady Pratt bpratt@redhat.com

Summary by CodeRabbit

  • Updated Quay CI configuration to target quay-v5.0.0 for the master branch.
  • Added the redhat-5.0 branch configuration with quay-v5.0.0 and quay-v5.0.z targets.
  • Enabled default validation for the new branch configuration.

@jbpratt
NO-ISSUE: chore: bump quay master version
ec46c49 
Signed-off-by: Brady Pratt <bpratt@redhat.com>
@openshift-ci-robot

openshift-ci-robot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@jbpratt: This pull request explicitly references no jira issue.

Details

In response to this:

Signed-off-by: Brady Pratt bpratt@redhat.com

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 7, 2026
@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 7, 2026
@openshift-merge-bot

openshift-merge-bot Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@jbpratt: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

@coderabbitai

coderabbitai Bot commented Aug 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: bbef5194-fc9a-4209-8162-ca6993e312fe

📥 Commits

Reviewing files that changed from the base of the PR and between ec91098 and ec46c49.

📒 Files selected for processing (1)
  • core-services/jira-lifecycle-plugin/config.yaml

Walkthrough

The Quay lifecycle configuration now targets quay-v5.0.0 for master and adds a redhat-5.0 branch targeting quay-v5.0.z with default validation enabled.

Changes

Quay lifecycle configuration

Layer / File(s) Summary
Update Quay branch targets
core-services/jira-lifecycle-plugin/config.yaml		 The master branch now targets quay-v5.0.0. The redhat-5.0 branch targets quay-v5.0.z, depends on quay-v5.0.0, and enables default validation.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: ezio-auditore

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the primary change: updating the Quay master version.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The commit changes only config.yaml; its diff contains no Ginkgo tests or test-title constructs, so this check is not applicable.
Test Structure And Quality ✅ Passed The commit changes only config.yaml and adds no Ginkgo test code, so the test-structure quality check is not applicable.
Microshift Test Compatibility ✅ Passed The commit changes only core-services/jira-lifecycle-plugin/config.yaml and adds no Ginkgo tests or test constructs, so MicroShift test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR changes only Jira lifecycle YAML configuration and adds no Ginkgo e2e tests, so SNO compatibility review does not apply.
Topology-Aware Scheduling Compatibility ✅ Passed The commit changes only Jira lifecycle YAML version mappings; it adds no deployment manifests, operator code, controllers, or scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The PR changes only Jira YAML configuration; it adds no process-level binary code or stdout writes, and the modified YAML parses successfully.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The commit changes only core-services/jira-lifecycle-plugin/config.yaml; it adds no Ginkgo e2e tests or network operations to assess.
No-Weak-Crypto ✅ Passed The commit changes only Quay YAML version and branch metadata; the six added lines contain no listed weak algorithms, crypto implementation, or secret/token comparison.
Container-Privileges ✅ Passed The PR changes only Jira branch-version configuration. Added lines contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed The patch changes only Quay target-version YAML entries. It adds no logging code, credentials, tokens, passwords, PII, hostnames, or customer data.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 7, 2026
@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bradmwilliams, jbpratt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 7, 2026
@jbpratt

jbpratt commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

@jbpratt: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot
openshift-merge-bot Bot merged commit b136251 into openshift:main Aug 10, 2026
8 checks passed
@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

@jbpratt: Updated the jira-lifecycle-plugin-config configmap in namespace ci at cluster app.ci using the following files:

  • key config.yaml using file core-services/jira-lifecycle-plugin/config.yaml
Details

In response to this:

Signed-off-by: Brady Pratt bpratt@redhat.com

Summary by CodeRabbit

  • Updated Quay CI configuration to target quay-v5.0.0 for the master branch.
  • Added the redhat-5.0 branch configuration with quay-v5.0.0 and quay-v5.0.z targets.
  • Enabled default validation for the new branch configuration.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

jzding pushed a commit to jzding/release that referenced this pull request Aug 11, 2026
@jbpratt @jzding
NO-ISSUE: chore: bump quay master version (openshift#83122)
fa55e8e 
Signed-off-by: Brady Pratt <bpratt@redhat.com>
TimurMP pushed a commit to TimurMP/release that referenced this pull request Sep 5, 2026
@jbpratt @TimurMP
NO-ISSUE: chore: bump quay master version (openshift#83122)
71f4030 
Signed-off-by: Brady Pratt <bpratt@redhat.com>
openshift-merge-bot Bot pushed a commit that referenced this pull request Sep 18, 2026
@jbpratt @claude
fix(jira-lifecycle): repair quay redhat-3.17 backport dependency (#85473
2a54bd7 
)

redhat-3.17 in quay/quay and quay/quay-operator declares a dependency on
target version quay-v3.18.0, which no branch has provided since master was
bumped off it on 2026-08-10 (#83122, later #83387). handleBackport resolves
dependent_bug_target_versions against the set of configured branch target
versions, so the unresolvable entry makes it report missing branches and
return before creating a Jira clone or queuing a cherrypick. redhat-3.16
depends on redhat-3.17 and is blocked by the same chain.

Point redhat-3.17 at quay-v3.18.z, the target version redhat-3.18 actually
has, matching the redhat-3.N -> quay-v3.(N+1).z convention every other
z-branch already uses.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
jtaleric pushed a commit to jtaleric/release that referenced this pull request Sep 23, 2026
@jbpratt @claude @jtaleric
fix(jira-lifecycle): repair quay redhat-3.17 backport dependency (ope…
be78883 
…nshift#85473)

redhat-3.17 in quay/quay and quay/quay-operator declares a dependency on
target version quay-v3.18.0, which no branch has provided since master was
bumped off it on 2026-08-10 (openshift#83122, later openshift#83387). handleBackport resolves
dependent_bug_target_versions against the set of configured branch target
versions, so the unresolvable entry makes it report missing branches and
return before creating a Jira clone or queuing a cherrypick. redhat-3.16
depends on redhat-3.17 and is blocked by the same chain.

Point redhat-3.17 at quay-v3.18.z, the target version redhat-3.18 actually
has, matching the redhat-3.N -> quay-v3.(N+1).z convention every other
z-branch already uses.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hoxhaeris hoxhaeris Awaiting requested review from hoxhaeris
1 more reviewer
@bradmwilliams bradmwilliams bradmwilliams approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

@bradmwilliams bradmwilliams

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@jbpratt @openshift-ci-robot @bradmwilliams